JENKINS-68116 Make event thread pool size customize-able #124
Conversation
|
I'm going to do some more log searching now that I've increased the amount of logs to see if there's anything useful. |
|
@jtnord @jenkinsci/scm-api-plugin-developers I've reduced the size to 10 for now by default but making is customiseable to at least unblock me. are we able to integrate just this change? FWIW this doesn't scale right now very well, see https://issues.jenkins.io/browse/JENKINS-68116?focusedCommentId=423884&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-423884 |
timja
changed the title
|
ping @jtnord |
timja
force-pushed
the
JENKINS-68116-make-thread-count-customise-able
branch
from
f7fbf52
to
a611e79
Compare
|
Ping @jtnord / @jenkinsci/scm-api-plugin-developers I've reduced our folder count from 68 to 6 which seems to be performing better but I would still like to be able to configure this above 10. It doesn't make sense for a 10 repository instance to have the same processing capacity as an org with over 1500 repositories |
timja
force-pushed
the
JENKINS-68116-make-thread-count-customise-able
branch
from
a611e79
to
62eb573
Compare
See https://issues.jenkins.io/browse/JENKINS-68116
Slow processing of events is causing delays of over an hour for our users to have their builds / pushes picked up
Currently increases thread pool size from 10 -> 30 and adds a system property to make it customise-able
Last changed in #61
I've ran this for four hours on a busy controller and never saw the queue grow above 4 or the thread pool get maxed out with running threads (highest I saw was ~27).
Running this in script console shows the status:
Related PR: jenkinsci/branch-api-plugin#304